Methods, systems and computer program products for associating records in healthcare databases with individuals

ABSTRACT

Methods, systems and computer program products for associating healthcare records in healthcare databases with an individual are provided. One or more attribute types are located in first and second records. The one or more attribute types being associated with the individual. A weighted score is determined for the located at least one attribute type based on a comparison of the located at least one attribute type in the first record and the located at least one attribute type in the second record. The weighted score indicates a likelihood that the located at least one attribute type in the first and second records are both associated with the individual. A confidence is provided and is associated with the first and second records based on the weighted score. The confidence score indicates a likelihood that both the first and second records are associated with the individual.

FIELD OF THE INVENTION

The invention relates to database management in general and, more particularly, to organization and verification of data stored in databases.

BACKGROUND OF THE INVENTION

As the field of healthcare continues to become more specialized, the provision of services by many healthcare workers and/or providers to many patients may increase. In order to accomplish this, healthcare delivery has been organized into specialized departments or healthcare sources such as, for example, nursing, laboratory, pharmacy, and radiology departments. Each department has the responsibility for accomplishing its particular, often specialized, subset of tasks. Sometimes the departments are associated with different healthcare enterprises or offices having different geographic locations. Unfortunately, this has resulted in sub-optimal healthcare operations because patient information related to a single patient that is stored at various departments may not be easily accessible from a single place.

Conventional healthcare information systems (HIS) combine patient related information for a particular patient from multiple, different healthcare sources into a single consolidated database, having a master patient index (MPI), using various record matching techniques. However, these systems may experience many problems and may not provide very accurate results. For example, the conventional record matching techniques may incorrectly combine two patient's information if two patient's have the same name. Furthermore, conventional record matching techniques may combine multiple copies of the same patient information creating a duplicate record or may not locate critical patient information that is related to the same patient, which may result in an improper diagnosis. Current matching techniques may generate an unacceptable number of false matches, duplicate matches and/or miss matches. Conventional methods for storing and/or accessing medical data in and/or from databases that attempt to address the problems discussed above, are discussed in, for example, United States Patent Publication Nos. US 2003/0088438 and US 2003/0177132. However, there is a need for improved record matching techniques to allow generation of a combined patient record that can be relied upon for the provision of healthcare to the patient.

SUMMARY OF THE INVENTION

Some embodiments of the present invention provide methods, systems and computer program products for associating healthcare records in healthcare databases with an individual. One or more attribute types are located in first and second records. The one or more attribute types are associated with the individual. A weighted score is determined for the located at least one attribute type based on a comparison of the located at least one attribute type in the first record and the located at least one attribute type in the second record. The weighted score indicates a likelihood that the located at least one attribute type in the first and second records are both associated with the individual. A confidence score associated with the first and second records is provided based on the weighted score. The confidence score indicates a likelihood that both the first and second records are associated with the individual.

In further embodiments of the present invention, logic may be applied to the weighted score to provide the confidence score. The first and second records may be located in first and second databases, respectively. The first and second databases may be the same database.

In still further embodiments of the present invention, one or more attribute types associated with the individual may be obtained from the first record in a first database on a local server. The obtained one or more attribute types may be located in the second record in a second database on a remote server. The attribute types may include a first name, last name, a social security number, a gender, a birth date, an address, a telephone number, a birth place, a blood type, an age, a height, a weight and/or a gene signature.

In some embodiments of the present invention, the individual may be assigned an identifier so as to allow future identification of the individual. The identifier may be associated with the first and second records if the confidence score meets a predetermined threshold. In certain embodiments of the present invention, the information in the first and second records may be combined into a third complete record if the confidence score meets a predetermined threshold.

In further embodiments of the present invention, a first attribute type associated with the individual may be located in the first and second records and a second attribute type may be located in the first and second records. A first weighted score may be determined based on a comparison of the located first attribute type in the first record and the located first attribute type in the second record and a second weighted score may be determined based on a comparison of the located second attribute type in the first record and the located second attribute type in the second record. The confidence score may be provided by applying logic to the first and second weighted scores.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating data processing systems according to some embodiments of the present invention.

FIG. 2 is a block diagram illustrating an exemplary network environment for operations and devices according to some embodiments of the present invention.

FIG. 3 is a schematic illustration of relationships between a database environment according to some embodiments of the present invention and existing HMO and/or hospital databases.

FIGS. 4A through 4D illustrate exemplary patient records and the type of data included therein according to some embodiments of the present invention.

FIG. 5 is flowchart illustrating operations according to some embodiments of the present invention.

FIG. 6 is flowchart illustrating operations according to further embodiments of the present invention.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

The invention now will be described more fully hereinafter with reference to the accompanying drawings, in which illustrative embodiments of the invention are shown. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items.

It will be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. Thus, a first element discussed below could be termed a second element without departing from the scope of the present invention.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

As will be appreciated by one of skill in the art, the invention may be embodied as a method, data processing system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Furthermore, the present invention may take the form of a computer program product on a computer-usable storage medium having computer-usable program code embodied in the medium. Any suitable computer readable medium may be utilized including hard disks, CD-ROMs, optical storage devices, a transmission media such as those supporting the Internet or an intranet, or magnetic storage devices.

Computer program code for carrying out operations of the present invention may be written in an object oriented programming language such as Java®, Smalltalk or C++. However, the computer program code for carrying out operations of the present invention may also be written in conventional procedural programming languages, such as the “C” programming language or in a visually oriented programming environment, such as VisualBasic.

The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

The invention is described in part below with reference to a flowchart illustration and/or block diagrams of methods, systems, computer program products and data structures according to embodiments of the invention. It will be understood that each block of the illustrations, and combinations of blocks, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function/act specified in the block or blocks.

The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the block or blocks.

Embodiments of the present invention will now be discussed with respect to FIGS. 1 through 6. As described herein, records located in one or more healthcare databases may be accurately associated with an individual. In particular, one or more attribute types, for example, gender, height, weight, blood type and the like, associated with the individual may be obtained. The attribute types may be obtained by, for example, entering the name of the individual into a first database and obtaining a first record in the first database having the name of the individual. The individual's name and/or the attribute types contained in the first record may be located in one or more additional records in the first database or in one or more remote databases. Similar attribute types in the located records may be compared. For example, if five records exist having the individual's name in the “name” field, the social security number attribute types in these records may be located and compared. A weighted score indicating the likelihood that the located attribute types (social security number) in the multiple records are associated with the same individual may be determined. For example, if the social security numbers in two records match, the weighted score may indicate that there is a 100 percent likelihood that both of the attribute types belong to the same individual. If, on the other hand, the social security numbers do not match, the weighted score may indicate that there is a 0 percent likelihood that both attribute types belong to the same individual. Using the weighted scores identified for each of the attribute types in the located records, a confidence score may be generated for each of the located records indicating the likelihood that the records belong to the same individual. For example, the confidence score for a particular record may indicate that there is a 92 percent likelihood that a record belongs to the individual. Thus, the confidence score may provide an indication of the accuracy of the matching process, which may be used to decide whether or not to provide medical services to the individual as discussed further herein below.

FIG. 1 illustrates an exemplary data processing system 100 or database environment that may be included in devices operating in accordance with some embodiments of the present invention. As illustrated, the data processing system 100 includes a processor 138, a memory 136 and input/output circuits 146. The data processing system 100 may be incorporated in, for example, a personal computer, server, router or the like. The processor 138 communicates with the memory 136 via an address/data bus 148 and communicates with the input/output circuits 146 via an address/data bus 149. The input/output circuits 146 can be used to transfer information between the memory 136 and another computer system or a network using, for example, an Internet protocol (IP) connection. These components may be conventional components such as those used in many conventional data processing systems, which may be configured to operate as described herein.

In particular, the processor 138 can be any commercially available or custom microprocessor, microcontroller, digital signal processor or the like. The memory 136 may include any memory devices containing the software and data used to implement the functionality circuits or modules used in accordance with embodiments of the present invention. The memory 136 can include, but is not limited to, the following types of devices: cache, ROM, PROM, EPROM, EEPROM, flash memory, SRAM, DRAM and magnetic disk. In some embodiments of the present invention, the memory 136 may be a content addressable memory (CAM).

As further illustrated in FIG. 1, the memory 136 may include several categories of software and data used in the data processing system 100: an operating system 152; application programs 154; input/output device drivers 158; and data 156. As will be appreciated by those of skill in the art, the operating system 152 may be any operating system suitable for use with a data processing system, such as OS/2, AIX or zOS from International Business Machines Corporation, Armonk, N.Y. Windows95, Windows98, Windows2000 or WindowsXP from Microsoft Corporation, Redmond, Wash. Unix or Linux. The input/output device drivers 158 typically include software routines accessed through the operating system 152 by the application programs 154 to communicate with devices such as the input/output circuits 146 and certain memory 136 components. The application programs 154 are illustrative of the programs that implement the various features of the circuits and modules according to some embodiments of the present invention. Finally, the data 156 represents the static and dynamic data used by the application programs 154, the operating system 152, the input/output device drivers 158, and other software programs that may reside in the memory 136. As illustrated in FIG. 1, the data 156 may include attribute type data 126 and patient identifier data 128 for use by the circuits and modules of the application programs 154 according to some embodiments of the present invention as discussed further herein.

As further illustrated in FIG. 1, according to some embodiments of the present invention the application programs 154 include a location circuit 120, a statistical module 122 and an identification circuit 124. The location circuit 120 may be configured to receive an input, such as, a name of an individual and/or an attribute type 126 associated therewith. The attribute types may be located in a record having the individual's name. The record may be located in a local database or a remote database. The individual may be a patient, physician or healthcare provider without departing from the scope of the present invention. As used herein, an “attribute type” refers to any category of information that may be associated with an individual that can be used for identification purposes. For example, attribute types according to some embodiments of the present invention may include, for example, first name, last name, social security number, gender, birth date, address, telephone number, birth place, blood type, age, height, weight, eye color, hair color, race and/or gene signature, such as a single nucleotide polymorphism (SNP). It will be understood that this list of attribute types is provided for exemplary purposes only and that embodiments of the present are not limited to the attribute types set out herein.

The location circuit 120 may be further configured to locate one or more records including the patient's name and/or attribute types associated therewith in multiple databases. For example, if the patient is a member of an HMO, the database for the HMO may include patient information associated with the patient. Furthermore, a hospital in which the patient has been treated may also have a database, which may include information about the patient. More than one record located using the patient's name and/or attributes associated therewith may be located in each of the databases.

The statistical module 122 may be configured to compare the attribute types located in the multiple records. For example, two patient records, one located in the HMO database and one located in the hospital database, may include an attribute type directed to blood type, the blood types in the two patient records may be compared to determine if they are the same. The statistical module 122 may be further configured to calculate a weighted score for the located attribute type based on the result of the comparison of the located at attribute types in the record of the HMO database and the record of the hospital database. The weighted score may indicate the likelihood that the attribute types located in the record of the HMO database and the record of the hospital database are both associated with the same individual. For example, if the blood types match, the weighted score may indicate a 100 percent likelihood that the attribute types both belong to the same individual. On the other hand, if the blood types do not match, the weighted score may indicate a 0 percent likelihood that the attribute types belong to the same individual. A weighted score may be calculated for each of the similar attribute types in the located records.

It will be understood that “comparing” or “comparison”, as used herein, refers not only to a simple comparison, i.e., the attribute types match or do not match, but also to a more complicated comparison that may assess the likelihood that two attribute types are similar enough to belong to the same patient or may have changed over the period of time between records. For example, hazel eyes may sometimes appear green and other times appear brown. Thus, an individual associated with a record indicating a hazel eye color may be the same individual associated with a record indicating a green eye color. Furthermore, it is common for people to change their hair color. Thus, an individual associated with a record indicating a brown hair color may be the same individual associated with a record indicating a red hair color. The fact that some attribute types may change over time or are subject to multiple interpretations may be taken into account in the calculation of the weighted score for the attribute type. Furthermore, attribute types that may change over time or are subject to different interpretations may be given less weight in the calculation of an overall confidence score than those attribute types that are fixed as discussed further below.

It will be further understood that devices and systems according to some embodiments of the present invention are capable of learning from the previous record comparisons. For example, if it is determined that two records belong to the same individual even though one of the records indicated eye color as brown and one of the records indicated eye color as hazel, devices and systems according to embodiments of the present invention may use this information and adjust the weighting given to these attribute types the next time this scenario occurs. Furthermore, devices and systems according to embodiments of the present invention may be also learn which computational logic and statistical algorithms obtain the best results and use these more frequently.

Although embodiments of the present invention are discussed above with respect to two databases, more than two databases may be searched without departing from the scope of the present invention. Furthermore, more than one record may be located in each database. For example, if a patient comes into the emergency room twice and on the first visit the healthcare provider enters her name spelled correctly and on the second visit the healthcare provider enters her name spelled incorrectly, this patient will have two records in the hospital's database. According to some embodiments of the present invention, the second record having the misspelled name may be located using other attribute types associated with the patient.

The identification circuit 124 may be configured to provide a confidence score based on the weighted score associated with each of the attribute types located in multiple records. For example, if three patient records having the name of the individual are located in three different databases, the statistical module 122 may be configured to calculate a weighted score for each of the attribute types that at least two of the records have in common. The identification circuit 124 may be further configured to use the generated weighted scores as an input and calculate an overall confidence score that indicates the likelihood that the located records belong to the same individual. If the confidence score indicates that there is a 99.9 percent likelihood that a record belongs to the individual, a healthcare provider may be able to rely on the information in these records in the provision of healthcare services to this individual. If, on the other hand, the confidence score indicates that there is only a 50 percent likelihood that the record belongs to the individual, this record may not be a reliable source for the provision of healthcare services. For example, if the record having a confidence score indicating a 50 percent likelihood that the record belongs to the individual indicates the individual's blood type, the healthcare provider may not wish to rely on this information, as provision of blood of the wrong type to a patient could cause serious damage. It will be understood that in some embodiments of the present invention, the confidence score is provided for illustrative purposes and may be spread for ease of understanding.

In some embodiments of the present invention, the identification circuit 124 may be configured to assign an identifier 128, which may be associated with the records located in each of the databases having a specified confidence score and/or the individual himself. The identifier 128 may be stored in, for example, a database on a device in a doctor's office, and may allow future identification of the individual and the records associated therewith. In certain embodiments of the present invention, the records located having a specified confidence score may be combined into a single record on a specific database, for example, the database at the doctor's office, or software links may be created between the local database at the doctor's office and the remote databases in which the records having a specified confidence score were located. Weighted scores may also be updated through the links as data from records stored at the remote databases are added to or combined with records stored at the local database.

In some embodiments of the present invention, the identification circuit 124 may apply computational logic and/or use statistical algorithms to generate the confidence score associated with the records. The computational logic and statistical algorithms that may be used are known to those having skill in the art and, therefore, will not be discussed further herein.

While the present invention is illustrated with reference to the location circuit 120, the statistical module 122 and the identification circuit 124 being application programs in FIG. 1, as will be appreciated by those of skill in the art, other configurations fall within the scope of the present invention. For example, rather than being application programs 154, these circuits and modules may also be incorporated into the operating system 152 or other such logical division of the data processing system 100. Furthermore, while the location circuit 120, the statistical module 122 and the identification circuit 124 are illustrated in a single data processing system, as will be appreciated by those of skill in the art, such functionality may be distributed across one or more data processing systems. Thus, the present invention should not be construed as limited to the configuration illustrated in FIG. 1, but may be provided by other arrangements and/or divisions of functions between data processing systems. For example, although FIG. 1 is illustrated as having various circuits and modules, one or more of these circuits or modules may be combined without departing from the scope of the present invention.

FIG. 2 illustrates an exemplary environment 200 for operations and devices according to some embodiments of the present invention. As illustrated in FIG. 2, the environment 200 may include a communications device 210, a network 220, a first server 240 and a second server 245. It will be understood that the communications device 210 illustrated in FIG. 2 may include the data processing system 100 or database environment discussed above with respect to FIG. 1. The communications device 210 may be, for example, a laptop computer, a desktop computer, a personal data assistant (PDA), a web capable mobile terminal or any device capable of communicating with the network 220. The communications device 210 may include a user interface 244, which may be used to enter a name of an individual and/or one or more attribute types associated therewith, and a web browser 215 that may be accessed through the user interface 244. The first and second servers 240 and 245 may include first and second database environments 230 and 235, respectively, which may include patient records for use in some embodiments of the present invention. The communications device 210 may communicate over the network 220, for example, the internet, through a telephone line, a digital subscriber link (DSL), a broadband cable link, a wireless link or the like. The first and second servers 240 and 245 may also communicate over the network 220. Thus, the network 220 may convey data between the communications device 210 and the first and second servers 240 and 245.

Exemplary operations of methods and devices according to some embodiments of the present invention will now be discussed with respect to FIG. 2. A patient may have an appointment at a doctor's office and may provide his name, John Doe, to the person doing intake at the doctor's office. The doctor's office may include a communications device 210 including a data processing system 100 or database environment according to embodiments of the present invention. The person doing intake at the doctor's office may enter the patient's name, John Doe, using the user interface 244 of the communications device 210. For example, the user interface 244 may be a graphical interface that requests such information as patient's name, address, phone number, social security number, blood type, and any other relevant attribute type. Alternatively, the patient's name may be used to provide access to a patient record or records stored in a database associated with the doctor's office. Devices and methods according to embodiments of the present invention may be configured to located records having names similar to the patient's name. For example, in this example, embodiments of the present invention may be configured to locate records having the following names associated therewith: Jonathon Doe, Jon Doe, John S. Doe, John Steven Doe and the like. This database may be stored at the communications device 210 or at a remote server associated with the communications device without departing from the scope of the present invention.

The web browser 215 may be used to access other healthcare databases to obtain more information about the patient and the patient's medical history. Using the web browser 215, the patient's name and the attribute types associated therewith may be used to access a first database environment 230 at a first server 240 and a second database environment 235 at a second server 245. The first and second database environments 230 and 235 may include patient records. The first database environment 230 may be associated with an HMO and the second database environment 235 may be associated with a hospital. The web browser 215 may communicate the patient's name and/or the attribute types associated therewith over the network 220 to the first and second servers 240 and 245. As discussed above, the patient's name and associated attribute types may be used to locate one or more patient records stored in the first and second database environments 230 and 235.

Exemplary database environments and patient records according to some embodiments of the present invention are illustrated in FIGS. 3 and 4, respectively. The example of John Doe will be discussed further with respect to FIGS. 2, 3 and 4. As illustrated in FIG. 3, a database environment 310 is provided at the doctor's office and has access to the HMO database 230 and the Hospital database 235 via the network 220. As further illustrated, each of the database environments 310, 230 and 235 include multiple patient records. In particular, database 310 includes three patient records 310 a, 310 b and 310 c, the HMO database 230 includes three patient records 230 a, 230 b and 230 c and the Hospital database 235 includes four patient records 235 a, 235 b, 235 c and 235 d. As illustrated, each of the databases has at least one patient record directed to a “John Doe,” i.e., patient records 310 a, 230 a, 235 a and 235 d. The details of the four patient records 310 a, 230 a, 235 a and 235 d are illustrated out in FIGS. 4A through 4D.

As illustrated in FIGS. 4A through 4D, each of the patient records 310 a, 230 a, 235 a and 235 d include data associated with one or more of the following attribute types: first name, last name, date of visit, gender, social security number, height, weight, date of birth (DOB), blood type, address and telephone number. As further illustrated, all of the records 310 a, 230 a, 235 a and 235 d do not necessarily include the same attribute types. Furthermore, patient record 310 a, which belongs to the patient, John Doe in this example, also includes a patient identifier, that may be associated with John Doe and used to access records associated with John Doe in accordance with some embodiments of the present invention as discussed further below. According to some embodiments of the present invention, once these records 310 a, 230 a, 235 a and 235 d are located, the similar attribute types in each of the located records 310 a, 230 a, 235 a and 235 d are compared. In particular, the attribute type associated with gender is provided in all four patient records 310 a, 230 a, 235 a and 235 d, and all four records 310 a, 230 a, 235 a and 235 d indicate that John Doe is male. Thus, the gender attribute type for each of the patient records 310 a, 230 a, 235 a and 235 d is given a weighted score indicating a 100 percent likelihood that all four records 310 a, 230 a, 235 a and 235 d belong to John Doe. However, because gender can only be either male or female, the gender attribute type may not be the most informative attribute type. Thus, the weighted score for gender may not be given as much consideration as other more informative attribute types in the calculation of the overall confidence score for the record as discussed further below.

The attribute type associated with Social Security No. (SS#) is provided in three records 310 a, 230 a and 235 d out of the four records 310 a, 230 a, 235 a and 235 d. The SS# attribute types match in two of the patient records 310 a and 230 a of the database 310 and the HMO database 230, respectively, but do not match the SS# attribute type in the patient record 235 d of the hospital database 235. Thus, the weighted score for the SS# attribute type assigned to the patient records 310 a and 230 a of the database 310 and the HMO database 230, may indicate a 100 percent likelihood that both of these records 310 a and 230 a belong to John Doe. However, the weighted score given to the SS# attribute type assigned to the patient record 235 d of the hospital database 235 may indicate a 0 percent likelihood that this record 235 a belongs to John Doe.

The reliability of the attribute type directed to social security number may depend on the facility in which the social security number is supplied. For example, in a public hospital in a large city, such as Atlanta, a social security number may not provide useful information due to a large number of illegal immigrants using the same social security number. In other words, multiple patients may be in the database having the same social security number, therefore, reducing the reliability of a match of this attribute type. However, in an exclusive private clinic, the use of the social security number for identification purposes may be so accurate as to be the only piece of information needed for identification. Thus, the weighting given to a particular weighted score when calculating the confidence score for the record may vary from institution to institution. Similarly, the weighting given to information found in the records may also be based on the system the information is provided from. In other words, some databases are more reliable than others. For example, if the information is provided from a “gold standard database,” the information provided from this database may be given a higher weight than other records to which it is being compared.

As further illustrated in FIGS. 4A through 4D, each of the four records 310 a, 230 a, 235 a and 235 d includes an attribute type directed to height. The height attribute type matches in two patient records 310 a and 235 a out of the four patient records 310 a, 230 a, 235 a and 235 d provided. Furthermore, the height attribute type provided in patient record 230 a is only off by an inch, but the height attribute type provided in the patient record 235 d is off by almost a foot. Accordingly, it is likely that the weighted score for the height attribute type assigned to the patient records 310 a and 235 a may indicate a 100 percent likelihood that both of these records belong to John Doe and the height attribute type assigned to the patient records 230 a may indicate almost a 100 percent likelihood that this record belongs to John Doe as a small variation in height measurement may be expected. However, the weighted score given to the height attribute type of patient record 235 d may be very low as a height variation of almost a foot would not be expected.

Each of the four records 310 a, 230 a, 235 a and 235 d also include an attribute type directed to weight. The weight attribute type does not match in any of the four patient records 310 a, 230 a, 235 a and 235 d provided. However, this may be expected as John Doe visited these facilities on different days and a slight weight fluctuation may be normal. In particular, the difference in weight between the patient record 310 a and the patient record 230 a is 30 pounds, which may indicate a non-match of records. However, the weights were measured over 3 years apart. It is feasible that someone could gain 30 pounds in three years. The time delta between the weight measurements may betaken into account when calculating the weighted score for these records. The difference in weight between the patient record 310 a and the patient record 235 a is only 7 pounds and the weights were measured over a year apart. Again, the time delta between the weight measurements may betaken into account when calculating the weighted score for these records. Finally, the difference in weight between the patient record 310 a and the patient record 235 d is 50 pounds and these weights were only measured three days apart, which may indicate a non-match of these records. In some embodiments of the present invention, a user of the communications device 210 may be prompted to answer a question with respect to the result of the comparison. In this example, the user of the communications device 210 may be prompted to decide the relevance of the difference in weights.

The attribute type associated with date of birth (DOB) is provided in three 310 a, 235 a and 235 d out of the four records 310 a, 230 a, 235 a and 235 d. The DOB attribute type match in the patient records 310 a and 235 a of the database 310 and the hospital database 235, but do not match the DOB attribute in the patient record 235 d of the hospital database 235. Thus, the weighted score for the DOB attribute type assigned to the patient records 310 a and 235 a of the database 310 and the hospital database 235, may indicate a 100 percent likelihood that both of these records belong to John Doe. However, the weighted score given to the DOB attribute type assigned to the patient record 235 d of the hospital database 235 may indicate a 0 percent likelihood that this record belongs to John Doe.

The attribute type associated with blood type is provided in three records 310 a, 230 a and 235 d out of the four records 310 a, 230 a, 235 a and 235 d. The blood type attribute types match in the patient records 310 a and 230 a of the database 310 and the HMO database 230, but do not match the blood type attribute in the patient record 235 d of the hospital database 235. Thus, the weighted score for the blood type attribute type assigned to the patient records 310 a and 230 a, may indicate a 100 percent likelihood that both of these attributes belong to John Doe. However, the weighted score given to the blood type attribute type assigned to the patient record 235 d may indicate a 0 percent likelihood that this attribute belongs to John Doe.

Finally, the attribute type associated with address is provided in two records 230 a and 235 a out of the four records 310 a, 230 a, 235 a and 235 d. The addresses in the two records 230 a and 235 a do not match. However, this may be expected as John Doe visited these facilities on different days two years apart and it is possible that he may have moved. Both addresses are in Houston Tex., which may be further evidence that these two records are both associated with John Doe. The time delta between the addresses and the fact that both addresses are in Houston may be taken into account when calculating the weighted score for these attribute types.

Once the weighted scores are calculated for all of the attribute types located in two or more databases as discussed above, a confidence score associated with the patient records 230 a, 235 a and 235 d may be calculated. As discussed above, in some embodiments of the present invention, the weighted scores may be calculated using computational logic and statistical algorithms known to those having skill in the art and, thus, will not be discussed further herein.

As discussed briefly above, when calculating the likelihood that two patient records belong to a same patient, for example, John Doe in this example, some attribute types may be given more weight in the calculation of the confidence score as discussed above. The amount of weight given may vary from institution to institution as well as based on the type of information the attribute type provides. For example, gender may be given less weight than blood type, which may be given less weight than gene signatures.

With respect to the specific example discussed above, it appears that patient record 235 d will not be presented as being associated with John Doe with a very high confidence score. For example, there may be a 5 percent or less likelihood that the John Doe associated with the patient record 235 d is the same John Doe associated with the patient record 310 a. On the other hand, the confidence score associated with patient records 230 a and 235 a may be very high and it is likely that these records belong to the same John Doe associated with patient record 310 a. In other words, the confidence score associated with patient records 230 a and 235 a may be 95 percent or higher.

It will be understood that the facility using devices and methods according to embodiments of the present invention may customize the confidence score to be met before a particular action is to take place. For example, if a patient will be a recipient of a medical procedure, the confidence score that should be met may berelatively high, for example, 95 percent or above. However, if the patient information is being used to forward a bill for medical services rendered, the confidence score to be met may be much lower, for example, 70 percent or higher.

In some embodiments of the present invention, when a high enough confidence score is met (threshold), for example, 95 percent or higher, the information in the records having these confidence scores, patient records 230 a and 235 a in this example, may be incorporated in the record 310 a of the database environment 310. Alternatively, the database environment 310 may be configured to have links so as to allow access to patient records 230 a and 235 a as illustrated in patient record 310 a. Furthermore, the patient identification number associated with patient record 310 a may be associated with patient records 230 a and 235 a so as to allow future access to these records very quickly by providing the patient identification number. The identification number may be associated with a whole patient record or each piece of information (attribute-type) contained in the record without departing from the scope of the present invention.

It will be further understood that although exemplary embodiments of the present invention are discussed herein with respect to identification and verification of patient records, embodiments of the present invention are not limited to this configuration. For example, techniques used by devices and methods of the present invention may be used to identify physicians and/or other healthcare professionals without departing from the scope of the present invention. Thus, some embodiments of the present invention may be used to match patients with their physicians. For example, if the output of the database indicates that the physician performing a trauma surgery at 2 AM on a particular patient is also the dean of the Medical school, the confidence score associated with this physician/ patient match may be very low.

Operations according to some embodiments of the present invention will now be discussed with respect to FIGS. 5 and 6. Referring now to FIG. 5, operations begin at block 505 by locating at least one attribute type associated with an individual, for example, a patient or physician, in first and second records. The at least one attribute may be, for example, a social security number, a gender, a birth date, an address, a telephone number, a birth place, a blood type, an age, a height, a weight and/or a gene signature. The first and second records may be located in first and second databases, respectively, associated with an HMO and a hospital, respectively. A weighted score for the located at least one attribute type is determined based on a comparison of the located at least one attribute type in the first record and the located at least one attribute type in the second record (block 510). The weighted score may indicate the likelihood that the located at least one attribute type in the first and second records are associated with the individual. A confidence score may be provided that is associated with the first and second records based on the weighted scores (block 515). The confidence score may indicate a likelihood that both the first and second records are associated with the individual.

Referring now to FIG. 6, operations begin at block 600 by obtaining at least one attribute type associated with the individual from a first record in a first database on a local server. For example, a patient, John Doe, may enter a hospital using a database according to some embodiments of the present invention, and his name “John Doe” is entered into the database. Attribute types associated with John Doe may be provided from a record on a hospital database. The attribute types provided may be located in a second record in a second database, for example, a database associated with an HMO or a hospital (block 605). A weighted score for each of the located attribute types is determined based on a comparison of the located attribute types in the first and second records (block 610). The weighted score may indicate the likelihood that the located at least one attribute type in the first and second records are associated with the individual. A confidence score may be provided that is associated with the first and second records based on the weighted scores (block 615). The confidence score may indicate a likelihood that both the first and second records are associated with the individual. Once it has been determined that the record including the located attribute types belongs to the individual, an identification number may be associated with the records and/or the attribute types themselves or the information in the record may be combined with the information from the first record to create a single unified record associated with John Doe (block 620). This identification number may be used to access patient records associated with John Doe more easily in the future.

As briefly discussed above with respect to FIGS. 1 through 6, some embodiments of the present invention provide devices and methods for verifying that patient records stored in multiple databases are associated with a same patient or individual. Computational logic and statistical algorithms may be used to provide, to a specified confidence score, a likelihood that the records in the databases belong to a same individual. Thus, embodiments of the present invention may allow the number of false positive and/or negative identifications of patients to be reduced.

Many alterations and modifications may be made by those having ordinary skill in the art, given the benefit of present disclosure, without departing from the spirit and scope of the invention. Therefore, it must be understood that the illustrated embodiments have been set forth only for the purposes of example, and that it should not be taken as limiting the invention as defined by the following claims. The following claims are, therefore, to be read to include not only the combination of elements which are literally set forth but all equivalent elements for performing substantially the same function in substantially the same way to obtain substantially the same result. The claims are thus to be understood to include what is specifically illustrated and described above, what is conceptually equivalent, and also what incorporates the essential idea of the invention. 

1. A method of associating healthcare records in healthcare databases with an individual, comprising: locating at least one attribute type in first and second records, the at least one attribute type being associated with the individual; determining a weighted score for the located at least one attribute type based on a comparison of the located at least one attribute type in the first record and the located at least one attribute type in the second record, the weighted score indicating a likelihood that the located at least one attribute type in the first and second records are associated with the individual; and providing a confidence score associated with the first and second records based on the weighted score, the confidence score indicating a likelihood that the first and second records are associated with the individual.
 2. The method of claim 1, wherein providing the confidence score comprises applying logic to the weighted score.
 3. The method of Claim 1, wherein the first and second records are located in first and second databases, respectively.
 4. The method of claim 3, wherein the first and second databases are the same database.
 5. The method of claim 1, wherein locating the at least one attribute type comprises: obtaining the at least one attribute type associated with the individual from the first record in a first database on a local server; and locating the obtained at least one attribute type in the second record in a second database on a remote server.
 6. The method of claim 1, wherein the at least one attribute type comprises a first name, last name, a social security number, a gender, a birth date, an address, a telephone number, a birth place, a blood type, an age, a height, a weight, eye color, hair color, race and/or a gene signature.
 7. The method of claim 1, further comprising: assigning the individual an identifier so as to allow future identification of the individual; and associating the identifier with the first and second records if the confidence score meets a predetermined threshold.
 8. The method of claim 1, further comprising combining information in the first and second records into a third complete record if the confidence score meets a predetermined threshold.
 9. The method of claim 1: wherein locating at least one attribute type comprises locating a first attribute type associated with the individual in the first and second records and locating a second attribute type associated with the individual in the first and second records; wherein determining a weighted score comprises determining a first weighted score based on a comparison of the located first attribute type in the first record and the located first attribute type in the second record and determining a second weighted score based on a comparison of the located second attribute type in the first record and the located second attribute type in the second record; and wherein providing the confidence score comprises applying logic to the first and second weighted scores to provide the confidence score associated with the first and second records based on the first and second weighted scores.
 10. The method of claim 1, carried out by a computer program product embodied in a computer readable medium.
 11. A method of associating healthcare records in healthcare databases with an individual comprising providing a confidence score associated with first and second records based on a comparison of at least one attribute type located in the first record and the second record, the confidence score indicating a likelihood that both the first and second records are associated with the individual.
 12. The method of claim 11, carried out by a computer program product embodied in a computer readable medium.
 13. A system for associating healthcare records in healthcare databases with an individual, comprising: a location circuit configured to locate at least one attribute type in first and second records, the at least one attribute type being associated with the individual; a statistical module configured to compare the located at least one attribute type in the first record and the located at least one attribute type in the second record and determine a weighted score based on the comparison indicating a likelihood that the located at least one attribute type in the first and second records are both associated with the individual; and an identification circuit configured to provide a confidence score associated with the first and second records based on the weighted score, the confidence score indicating a likelihood that both the first and second records are associated with the individual.
 14. The system of claim 13, wherein the identification circuit is further configured to apply logic to the weighted scores to provide the confidence score.
 15. The system of claim 13, wherein the first and second records are located in first and second databases, respectively.
 16. The system of claim 15, wherein the first and second databases are the same database.
 17. The system of claim 13, wherein the location circuit is further configured to: obtain the at least one attribute type associated with the individual from the first record in a first database on a local server; and locate the obtained at least one attribute type in the second record in a second database on a remote server.
 18. The system of claim 13, wherein the at least one attribute type comprises a first name, a last name, a social security number, a gender, a birth date, an address, a telephone number, a birth place, a blood type, an age, a height, a weight, eye color, hair color, race and/or a gene signature.
 19. The system of claim 13, wherein the identification circuit is further configured to: assign the individual an identifier so as to allow future identification of the individual; and associate the identifier with the first and second records if the confidence score meets a predetermined threshold.
 20. The system of claim 13, wherein the identification circuit is further configured to combine information in the first and second records into a third complete record if the confidence score meets a predetermined threshold. 